Tortun Nahme
Minmatar
Heimatar Services Conglomerate
   |
Posted - 2008.02.16 07:50:00 -
[1]
 Originally by: Tarminic
Edited by: Tarminic on 15/02/2008 22:08:12
Originally by: Elles D
I was about to protest that it would be so simple to keep it, but i'll go with your view Tarminic as tbh i know bugger all about coding.
It's a shame, but if there is no easy way round it then it has to go unfortunately 
I can explain it a bit more thoroughly.
Adding a timer to containers is a relatively simple process. Basically you add to a single block of code that defines the behavior of all objects of that time.
To make an exception for the cemetery, you would have to do one of the following:
1. Have every single container check what system it's in at each downtime - this puts extra strain on the database for no good reason and is a bad coding practice (I can explain if you want, but it's complicated and technical).
2. Create a routine that checks all containers to see if they're in that system and increment their expiration date during downtime. This is also lag-intensive
Then of course, you have people that will continually spam that particular system with cans because they won't be deleted.
You could limit it to that particular planet but then people could spam the graveyard with unrelated cans. This would be popular because the graveyard would become a popular tourist location (just look at the cans at the EVE Gate!).
I really don't see any way around it. You could even check the text of the can's name for something like "RIP ", but then people would spam with cans that would say "Contact djfslkjf for all your farming needs! RIP "
There's really no good way around it. 
Originally by: Qanael Radlari
Maybe they could code it so cans have a GM-settable "permanent" flag, that could be applied given a proper petition and a good cause. That shouldn't be all that complicated. They could restrict it only to worthy causes, like RL memorial cans and the cemetery.
That is the most realistic solution, though it's still time-intensive on the part of the GMs...
you are missing the rather simple and elegant solution of simply changing the already existing cans in that batch to a different form of reference in the database to prevent them from being called in the can expiration script, or the slightly more exploitable possibility of preventing anchored cans with corpses in them from decaying, or any number of other equally simple solutions, though simply changing the exiting cans ref=id so that they arent called is the best bet to keep the monument
Originally by: Cecil Montague
They should change that warning on entering low sec to:
"Go read Crime and Punishment for a few days then come back."
|